Resource allocation device and resource allocation method

ABSTRACT

A resource allocation device includes a searcher configured, in response to a use request for resources of a physical network, the use request having a pair of nodes as terminal points designated among a plurality of nodes constituting the physical network, to search for one or more candidate paths between the terminal points, with which amounts of the resources related to the use request can be allocated, in a state where the resources that have already been allocated to one or more other use requests are set aside from the physical network; a calculator configured to calculate, for each of the one or more searched-for candidate paths, in a state where the resources are allocated to the candidate path, for each of the one or more other existing use requests to which the resources have already been allocated, a maximum number of paths that can be allocated between the terminal points related to the use request; and a selector configured to select the candidate path with which a sum total of the maximum numbers of paths becomes greatest. This enables resource allocation by which fragmentation of resources of a physical network can be avoided, a great number of services can be held in the physical network.

TECHNICAL FIELD

The present invention relates to a resource allocation device and a resource allocation method.

BACKGROUND ART

Progress of virtualization technologies has extended applicability of the virtualization technologies not only in the field of cloud computing but also in the field of communication networks. For example, the 5th generation mobile communication networks conceptualize flexible network control by application of the virtualization technologies. In virtualization of communication networks, the NFV (Network Functions Virtualization) technology enables to provide service functions of a communication service provider as software on general-purpose servers, which have conventionally been implemented by dedicated hardware such as routers and gateways. Therefore, a service function becomes executable on any server that exists on the network. Also, the SFC (Service Function Chaining) technology enables to transmit a packet flow of a user to a designated service function in a designated order, and thereby, enables to readily combine service functions. By utilizing these virtualization technologies, a service provider can provide flexible services by readily utilizing network resources and service functions prepared in advance on a communication network.

Meanwhile, a network provider who carries out operational management of such a communication network allocates network resources of its own to a service based on a request from a service provider. In order to raise investment efficiency of facilities, it is important for the network provider to hold as many services as possible on the invested physical network resources.

Allocation of physical network resources to requested services is called “VNE (Virtual Network Embedding) problem”, on which a significant number of researches have been reported in recent years (e.g., Non-patent document 1, Non-patent document 2, Patent document 1, etc.). The VNE problem is a problem of allocating physical network resources to services such that requirements of the services are satisfied, in which a given physical network is modeled as a weighted, undirected graph. A physical network is constituted with transfer nodes represented by routers, service nodes to execute service functions, and links that connect these nodes. Service nodes are assumed to be scattered all over the network rather than located in an aggregated site such as a cloud. Among various resource allocation policies that have been proposed, the most frequently used one is minimization of resource usage. In terms of physical resources to be allocated, it is often the case that the link bandwidth between transfer nodes, the CPU, memory, and storage of a service node, and the like are taken into account. Requirements for each service include transfer bandwidth, the upper bound of transfer latency, types and order of service functions to be received on the way. The above-mentioned physical resources are allocated in a way to satisfy such requirements.

In Non-patent document 1 and Non-patent document 2, although parameters taken into consideration are different, the objective is to minimize physical resources to allocate. In Patent document 1, network links and servers having greater numbers of residual resources (having lighter loads) are prioritized when allocated to a service so as to equalize the entire resource allocation.

RELATED ART DOCUMENTS Non-Patent Documents

-   Patent document 1: Japanese Unexamined Patent Application     Publication No. 2014-171056

Non-Patent Documents

-   Non-patent document 1: M. Yu et al., Rethinking Virtual Network     Embedding: Substrate Support for path Splitting and Migration, ACM     SIGCOMM Computer Communication Review, Vol. 38, No. 2, pp. 17-29,     2008 -   Non-patent document 2: M. Chowdhury et al., Vineyard: Virtual     network embedding algorithms with coordinated node and link mapping,     IEEE/ACM Trans. Networking, vol. 20, no. 1, pp. 206-219, 2012

SUMMARY OF INVENTION Problem to be Solved by the Invention

Although conventional technologies disclosed in Non-patent document 1, Non-patent document 2, and Patent document 1 aim at minimization or equalization of resources to allocate, they do not necessarily lead to maximization of the number of services that can be provided. This is because there is likelihood that the conventional technologies cause fragmentation of remaining resources. Similar to fragmentation of a computer memory, fragmentation of remaining resources here is a state in which usable resources are scattered, and hence, contiguous resources cannot be obtained in accordance with a new service request. In such a state, even if there is a margin in the total amount of remaining resources, resources may not be allocated to a new service, and consequently, the resource use rate declines. In particular, in the case of minimizing the amount of resources to allocate, there is a tendency that the resource usage increases on specific paths, and fragmentation tends to occur. Although fragmentation can be prevented to a certain extent by equalizing resources to allocate, an optimal allocation may not necessarily be obtained.

In a computer memory, if fragmentation occurs, it is possible to increase usable vacant areas by relocating resources being used. Similar consideration has been made in virtual networks.

However, since relocation of resources in a virtual network may lead to temporary discontinuance of network services, it is desirable to locate resources without necessity of relocation as much as possible.

The present invention has been made in view of the above respects, aiming at enabling allocation of resources that can avoid fragmentation of resources, and thereby, can hold many services in the physical network.

Means for Solving the Problem

Thereupon, in order to solve the above problems, a resource allocation device includes a searcher configured, in response to a use request for resources of a physical network, the use request having a pair of nodes as terminal points designated among a plurality of nodes constituting the physical network, to search for one or more candidate paths between the terminal points, with which amounts of the resources related to the use request can be allocated, in a state where the resources that have already been allocated to one or more other use requests are set aside from the physical network; a calculator configured to calculate, for each of the one or more searched-for candidate paths, in a state where the resources are allocated to the candidate path, for each of the one or more other existing use requests to which the resources have already been allocated, a maximum number of paths that can be allocated between the terminal points related to the use request; and a selector configured to select the candidate path with which a sum total of the maximum numbers of paths becomes greatest.

Advantage of the Invention

It is possible to enable allocation of resources that can avoid fragmentation of resources, and can accommodate many services in the physical network.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram for illustrating an overview of an embodiment of the present invention;

FIG. 2 is a diagram illustrating an example of a system configuration in an embodiment of the present invention;

FIG. 3 is a diagram illustrating an example of a hardware configuration of a resource allocation device in an embodiment of the present invention;

FIG. 4 is a diagram illustrating an example of a functional configuration of a resource allocation device in an embodiment of the present invention;

FIG. 5 is a sequence chart for illustrating an example of processing steps executed by a resource allocation device;

FIG. 6 is a flowchart for illustrating an example of processing steps of calculation of resource allocation;

FIG. 7 is a diagram for illustrating a specific example of an embodiment of the present invention;

FIG. 8 is a diagram illustrating an example of resource allocation to a virtual path 4 in a residual network;

FIG. 9 is a diagram illustrating a result of resource allocation obtained by an algorithm for minimizing resource usage;

FIG. 10 is a diagram illustrating a result of resource allocation obtained by an algorithm for equalizing resource use rate; and

FIG. 11 is a diagram illustrating a result of resource allocation obtained by an algorithm of an embodiment.

EMBODIMENTS OF THE INVENTION

In the following, embodiments will be described with reference to the drawings. FIG. 1 is a diagram for illustrating an overview of an embodiment of the present invention. In the present embodiment, suppose that multiple services are provided on a single physical network. As illustrated in the lower part in FIG. 1, a physical network is constituted with transfer nodes, service nodes to execute service functions, and links that connect the nodes. A transfer node is, for example, a router. A service node is, for example, one or more server computers.

Resources of the physical network allocated to services are divided into two types, namely, transfer-related resources and server-related resources. A transfer-related resource mainly indicates a resource of a link between transfer nodes in which the transfer bandwidth and the like specifically set for the link are taken into consideration. The transfer latency is set to each link in addition to the transfer bandwidth. A server-related resource indicates a resource of a service node in which CPU, memory capacity, storage capacity, and the like are specifically taken into consideration.

Meanwhile, as illustrated in the upper part in FIG. 1, requirements for providing a service, such as the transfer bandwidth, upper bound of transfer latency, service function, and the like are set in each service. The starting point and ending point of a service may be different for the same service depending on the user. For example, paths allocated should be different for a user in Tokyo and a user in Okinawa. Therefore, a “virtual path” is defined for each user of a service, as a path that includes designation of one of the pairs of nodes among multiple nodes constituting the physical network, in addition to the requirements for the service. Either a transfer node or a service node is selected as the starting point or the ending point. Resource allocation is executed in units of virtual paths. Requests for resource allocation to virtual paths arrive sequentially, and physical resources are allocated upon each request. In the present embodiment, for requests for resource allocation to virtual paths that arrive in time series, resource allocation is executed so as to prevent fragmentation of the resources and to improve the use efficiency.

FIG. 2 is a diagram illustrating an example of a system configuration in an embodiment of the present invention. As illustrated in FIG. 2, a system in the present embodiment includes a resource allocation device 10, multiple transfer nodes R (R₁ to R₇), and multiple service nodes S (S₁ to S₃).

Each of the transfer nodes R is provided with a function that is capable of controlling a transfer path of traffic by software, such as SDN (Software Defined Network), and the transfer path is controlled by the resource allocation device 10.

The service nodes S are commonly capable of executing service functions implemented by software, and the service functions can be executed on any of the service nodes. Management on which of the services is executed on which of the service nodes S is executed by the resource allocation device 10. Such management can be implemented by using a general NFV (Network Functions Virtualization), SFC (Service Function Chaining), or the like.

FIG. 3 is a diagram illustrating an example of a hardware configuration of a resource allocation device in an embodiment of the present invention. The resource allocation device 10 in FIG. 3 includes a drive unit 100, an auxiliary storage unit 102, a memory unit 103, a CPU 104, and an interface unit 105, which are mutually connected by a bus B.

A program that implements processing on the resource allocation device 10 is provided with a recording medium 101 such as a CD-ROM. Once the recording medium 101 storing the program is set in the drive unit 100, the program is installed into the auxiliary storage unit 102 from the recording medium 101 via the drive unit 100. However, installation of the program is not necessarily executed from the recording medium 101, and may also be downloaded from another computer via the network. The auxiliary storage unit 102 stores the installed program, and stores required files, data, and the like as well.

Upon receiving a command to activate the program, the memory unit 103 reads out the program from the auxiliary storage unit 102, to load the program. The CPU 104 executes a function related the resource allocation device 10, based on the program loaded in the memory unit 103. The interface unit 105 is used as an interface for connecting with a network.

FIG. 4 is a diagram illustrating an example of a functional configuration of a resource allocation device in an embodiment of the present invention. In FIG. 4, the resource allocation device 10 includes a service input unit 11, a resource allocator 12, a network path controller 13, and a service function controller 14. These units are implemented by processes which one or more programs installed in the resource allocation device 10 cause the CPU 104 to execute. The resource allocation device 10 also utilizes databases including a service function DB 15, a facility information DB 16, and a resource allocation DB 17. These databases can be implemented, for example, by using the auxiliary storage unit 102 or a storage device or the like that can be connected to the resource allocation device 10 via a network.

The service input unit 11 newly receives input from an operator of a service provider that specifies requirements for a virtual path to which resources are allocated.

The resource allocator 12 allocates resources to the virtual path based on the new requirements for the virtual path and information stored in each of the service function DB 15, the facility information DB 16, and the resource allocation DB 17. A result of resource allocation is represented as a resource allocation path. In an example of a virtual path 1 in FIG. 2, the resource allocation path passes through “user=>R₁=>R₂=>S₁ (function A)=>R₂=>R₅=>R₇=>S₂ (function C)=>R₇=>Internet”. The resource allocator 12 directs the network path controller 13 and the service function controller 14 to allocate resources based on the resource allocation path. Note that the resource allocator 12 includes a residual network generator 121, a candidate path searcher 122, a capacity calculator 123, and a path selector 124.

The network path controller 13 controls a path through the transfer nodes R based on the resource allocation path. The service function controller 14 controls the service nodes based on the resource allocation path. The network path controller 13 and the service function controller 14 interoperate to execute processing, and control transfer paths and execution of service functions based on paths allocated to respective virtual paths, to allocate physical resources.

The service function DB 15 stores, for each service function, the amounts of resources to be consumed by execution of the service functions (for example, for a function A, two cores of CPU, 1 GB of memory, and 10 GB of storage). The facility information DB 16 stores information on a physical network, including connection information (topological information) between the transfer nodes R and the service nodes S, the transfer bandwidth and transfer latency of each link, and the server capacity (the number of CPU cores, memory capacity, storage capacity, etc.). The resource allocation DB 17 stores, for each of the transfer-related resources (links) and the server-related resources (service nodes S), resource information that has already been allocated to existing virtual paths. For example, information representing an allocated bandwidth is stored for a transfer-related resource. Information representing an allocated server capacity is stored for a server-related resource.

In the following, processing steps executed by the resource allocation device 10 will be described. FIG. 5 is a sequence chart for illustrating an example of processing steps executed by the resource allocation device.

For example, in response to newly receiving input of requirements related to a virtual path from an operator of a service provider (Step S101), the service input unit 11 makes a request for resource allocation based on the requirements to the resource allocator 12 (Step S102). Note that in the requirements, a transfer bandwidth, a transfer latency, a service function, and the like required for providing a service are designated. Also, a starting point and an ending point of a service are designated in a virtual path for the user of the service.

The resource allocator 12 reads out required information from the DBs in response to the request. The amounts of resources consumed by the service designated in the requirements (the number of CPU cores, memory capacity, storage capacity, and the like) are obtained from the service function DB (Steps 5103 and S104). Information on the physical network, including connection information (topological information) between the transfer nodes R and the service nodes S, the transfer bandwidth and transfer latency of each link, the server capacity, and the like, is obtained from facility information DB 16 (Steps S105 and S106). Information on resources that have already been allocated to existing virtual paths is obtained from the resource allocation DB 17 (Steps S107 and S108).

Next, based on the requirements for the virtual path and the information obtained from the DBs, the resource allocator 12 calculates a resource allocation path (Step S109). Next, the resource allocator 12 directs each of the network path controller 13 and the service function controller 14 to allocate resources based on the calculated resource allocation path (Steps S110 and S111).

The network path controller 13 executes settings on transfer nodes R related to the resource allocation path (Step S112). Specifically, a path setting (a routing setting) is executed on the transfer node R for forming the resource allocation path. Also, the service function controller 14 executes settings on service nodes S related to the resource allocation path (Step S113). For example, on the service node S, a setting is executed that enables to provide the service function (for example, activation of the service function or the like). The resource allocator 12 also updates the content of the resource allocation DB 17, based on the resource allocation path (Step S114). For example, the transfer bandwidth of a link related to the resource allocation path may be decreased, and the server capacity of the service node S related to the resource allocation path may be decreased.

Next, Step S109 will be described in detail.

A path to be allocated to a new virtual path by the resource allocator 12 is selected so as to prevent fragmentation of the resources as much as possible, and to maximize the amount of usable remaining resources. Specifically, a path to be allocated is selected so as to maximize the total number of virtual paths to which resources can be allocated for existing services in the physical network (referred to as “service capacity”, below) if the designated resources are allocated to the new virtual path. In other words, as a path to be allocated to the new virtual path, a path that would not be used by other services is selected as much as possible. Consequently, it becomes possible to hold a greater number of contiguous resources available for the services as a whole, and the expected value of the number of services to be held can be increased more than in the conventional technologies.

FIG. 6 is a flowchart for illustrating an example of processing steps of calculation of resource allocation.

Once a request for a new virtual path has come from the service input unit 11 at Step S201, the residual network generator 121 reads out required information from the DBs (Step S202). The content of Step S202 is as having described with Steps S103-S108 in FIG. 5.

Next, the residual network generator 121 generates a weighted, undirected graph G (referred to as the “network G”, below) based on topological information on a physical network obtained from the facility information DB 16 (Step S203). For each edge in the network G, a transfer latency obtained from the facility information DB 16 is assigned as the weight. A capacity constraint (transfer bandwidth) obtained from the facility information DB 16 for each link is also set to each of the edges.

Next, the residual network generator 121 generates a virtual network from the network G (referred to as the “residual network G⁻”, below), in which the resource capacity that has already been allocated to existing virtual paths (for which the requests have arrived before the arrival of the request for the new virtual path, and currently uses the resources) is deducted (Step S204). In other words, the residual network G⁻ is a network that represents a state of the network G in which the resource capacity that has already been allocated to existing virtual paths is set aside. Note that the resource capacity that has already been allocated can be identified based on information obtained from the resource allocation DB 17.

Next, the candidate path searcher 122 searches for every candidate path A that satisfies the requirements for the virtual path in the residual network G⁻ (Step S205). In other words, every path to which the amounts of resources related to the requirements between the starting point and the ending point of the virtual path (between the terminal points) can be allocated, is searched for as the candidate path A. Note that such search for the candidate paths A can be executed by using any well-known algorithm.

Next, the candidate path searcher 122 determines whether the number of the candidate paths A or |A| is 0 (Step S206). If |A| is 0 (YES at Step S206), allocation fails because there is no allocatable path.

If |A| is greater than or equal to 1 (NO at Step S206), the resource allocator 12 determines whether |A| is 1 (Step S207). If |A| is 1 (YES at Step S207), the resource allocator 12 selects the one candidate path that has been found as the resource allocation path (Step S208).

On the other hand, if |A| is greater than or equal to 2 (NO at Step S207), the resource allocator 12 selects an optimal path from among the candidate paths A at Steps S209 and S210.

Here, service capacity in the network G, or v(G) is defined. The service capacity is a measure to represent how many of existing services can be held in a certain network G. The service capacity of the entire network is defined as the sum total of the capacity v_(s)(G, s) of each service s.

v _(g)(G)=Σ_(sϵS) v _(s)(G, s)

where S represents a set of existing services provided on the network G; and v_(s)(G,$) represents the capacity of an individual service s, which is defined as a value obtained by multiplying a maximum number of virtual paths that can be held for the service in the network G, by the weight of the service s.

v _(s)(G, s)=Σ_((x,y)ϵNs) W _(x,y,s)×maxpass(G, x, y, s)

where Ns represents a set (starting point, ending point) of virtual paths in the service s; and maxpass(G, x, y, s) represents a maximum number of virtual paths that can be held between the starting point x and the ending point y of a certain virtual path with respect to the service s. The maximum number of virtual paths can be obtained by solving a well-known problem called the maximum flow problem. For example, if there is one virtual path for a certain service s, the maximum number of paths that can be held between the starting point and the ending point of the virtual path is the maximum number of virtual paths. Although the number of paths that can be held between the starting point and the ending point may differ depending on a method for allocating paths, the maximum number of virtual paths corresponds to the number of paths obtained by a method for allocating paths that gives a maximum number of paths that can be held, among all methods for allocating paths. Note that w_(x,y,s) is a weight that depends on the importance of a service and a path.

At Step S209, for each candidate path aϵA in the residual network G⁻, the capacity calculator 123 generates a residual network G^(a−) in the case that resources are allocated to the candidate path a, to calculate the capacity v_(g)(G^(a−)) with respect to the residual network G^(a−). In other words, for every candidate path a, the capacity v_(g)(G^(a−)) is calculated in a state where resources are allocated to the candidate path a in the residual network G. Note that the capacity v_(g)(G^(a−)) with respect to the residual network G^(a−) represents the sum total of the capacity v_(s)(G^(a−), s) for every existing virtual path in the residual network G^(a−). Therefore, at Step S209, for each candidate path a, the capacity v_(s)(G^(a−), s) is calculated for each existing virtual path, and further, the capacities v_(s)(G^(a−), s) are summed up to calculate v_(g)(G^(a−)).

Next, the path selector 124 selects a candidate path a with which the capacity v_(g)(G^(a−)) becomes the maximum as the resource allocation path (Step S210). If there are multiple candidate paths a having the same value of v_(g)(G^(a−)), a candidate path with which the transfer latency of the virtual path becomes the minimum may be selected if QoS (Quality of Service) is considered to be important; or a candidate path with which the path length becomes the minimum may be selected if the resource consumption is considered to be important.

Next, a specific example of the present embodiment will be described. FIG. 7 is a diagram for illustrating a specific example of an embodiment of the present invention.

As illustrated on the left side in FIG. 7, suppose that a simple physical network G is given. Three types of services (service numbers) are available, and requirements of the services are as follows: for a service 1, the required transfer bandwidth is 1 Gbps, the required transfer latency is 30 ms, and the service function on the way is A; for a service 2, the required transfer bandwidth is 3 Gbps, the required transfer latency is 15 ms, and the service function on the way is B; and for a service 3, the required transfer bandwidth is 2 Gbps, the required transfer latency is 10 ms, and the service function on the way is C. The resource usage consumed when executing the service functions are: one core of CPU, 1 GB of memory, and 100 GB of storage for the function A; two cores of CPU, 2 GB of memory, and 200 GB of storage for the function B; and three cores of CPU, 3 GB of memory, and 300 GB of storage for the function C. Suppose that contents of the requirements for virtual paths are as illustrated in Table T1, and requests for resource allocation to virtual paths for the services 1, 2, and 3 arrive serially and repeatedly.

Note that in Table T1, the virtual paths having No. 1 to 3, have resources allocated already. As an example of execution of an algorithm, a case will be described in which resources are allocated to a virtual path 4 (a virtual path indicated with No. 4 in Table T1). The residual network G′ in which resources that have been allocated to existing virtual paths are deducted from the physical network G is as illustrated in FIG. 8. In the residual network G′, candidate paths to be allocated to the virtual path 4 are six paths listed in Table T2. Calculating the service capacity v_(g)(G^(a−)) for each of the paths (assuming every weight w_(x,y,s) set to 1) singles out the candidate path 4 of a=4 as the candidate path with which the service capacity v_(g)(G^(a−)) becomes the maximum. Therefore, in this case, the candidate path 4 is selected as the resource allocation path with respect to the virtual path 4.

Next, under the network conditions illustrated in FIG. 7, allocatable numbers of virtual paths are compared among an algorithm for minimizing resource usage, an algorithm for equalizing resource use rate, and the algorithm of the present embodiment.

In the algorithm for minimizing resource usage, a candidate path with which the resource usage becomes the minimum is selected from among the candidate paths. If multiple candidate paths exist, one having the shorter transfer latency is selected.

In the algorithm for equalizing resource use rate, a candidate path is selected so as to equalize use rates (to minimize variance of use rates) of all the resources. If multiple candidate paths exist, one having the shorter transfer latency is selected as in the algorithm for minimizing resource usage.

For the above three algorithms, the respective numbers of allocatable virtual paths are compared in the case where resource allocation is executed sequentially starting from the virtual path 1 in Table T1. If the resource allocation fails halfway through, allocation to the virtual path is given up, and resource allocation to the next virtual path will be executed. Therefore, under this condition, the number of virtual paths to be allocated is nine at most.

FIG. 9 is a diagram illustrating a result of resource allocation obtained by the algorithm for minimizing resource usage. FIG. 10 is a diagram illustrating a result of resource allocation obtained by the algorithm for equalizing resource use rate. FIG. 11 is a diagram illustrating a result of resource allocation obtained by the algorithm of the present embodiment. Comparing the numbers of virtual paths to which the resource allocation has succeeded by the respective algorithms, which are seven for the algorithm for minimizing resource usage; seven for the algorithm for equalizing resource use rate; and nine for the algorithm of the present embodiment, the present embodiment turns out to be the most superior. Also, the network resource consumption rates are 74.7% for the algorithm for minimizing resource usage; 77.3% for the algorithm for equalizing resource use rate; and 100% for the present embodiment. Thus, the present embodiment can utilize the resources effectively. Meanwhile, the average transfer latency per path is 10.3 ms for the algorithm for minimizing resource usage; 13.1 ms for the algorithm for equalizing resource use rate; and 13.3 ms for the present embodiment. Thus, it is understood that the present embodiment allocates a path that is more roundabout than the conventional technologies.

From the above results, it is understood that the present embodiment deliberately allocates a roundabout path, which would not be used by the other services, to a virtual path having a longer required transfer latency so that virtual paths having shorter required transfer latencies tend to be passed through, and thereby, a greater number of virtual paths can be held. Meanwhile, in the case of using the algorithm for minimizing resource usage or the algorithm for equalizing resource use rate, such consideration is not taken, and resources are allocated in accordance with respective objective, which causes fragmentation of the resources and existence of virtual paths that cannot be held.

Specifically, since resources on the shortest path between R₁ and R₄ have been allocated to virtual paths having longer required transfer latencies (service 2 and service 3), resources cannot be allocated to a virtual path having a shorter required transfer latency (service 1).

Even if the order of requests for the virtual paths changes, by using the present embodiment, the number of virtual paths to which resource allocation succeeds is always nine the greatest, and thus, a stable result can be derived regardless of conditions. Note that when using the other algorithms, the number of allocatable virtual paths varies depending on the order.

As described above, according to the present embodiment, when allocating physical resources to services in a virtual network, it is possible to prevent fragmentation of the resources as much as possible, and to maximize the amount of usable remaining resources. In other words, the present embodiment enables resource allocation by which fragmentation of resources of a physical network can be avoided. For example, it is possible to maximize an expected value of the number of services to be held in future, and to make the number of services to be held greater than those obtained by the conventional technologies. Consequently, a network provider can raise investment efficiency of facilities.

Note that in the present embodiment, a service request or a virtual path is an example of a use request for resources of a physical network; the candidate path searcher 122 is an example of a searcher; the capacity calculator 123 is an example of a calculator; and the path selector 124 is an example of a selector.

As above, the embodiments of the present invention have been described in detail. Note that the present invention is not limited to such specific embodiments, but various variations and modifications may be made within the scope of the subject matters of the present invention described in the claims.

The present patent application claims priority based on Japanese Patent Application No. 2015-222640 filed on Nov. 13, 2015, and entire contents of the Japanese Patent Application are incorporated herein by reference.

LIST OF REFERENCE SYMBOLS

-   10 resource allocation device -   11 service input unit -   12 resource allocator -   13 network path controller -   14 service function controller -   15 service function DB -   16 facility information DB -   17 resource allocation DB -   100 drive unit -   101 recording medium -   102 auxiliary storage unit -   103 memory unit -   104 CPU -   105 interface unit -   121 residual network generator -   122 candidate path searcher -   123 capacity calculator -   124 path selector -   B bus 

1. A resource allocation device comprising: a searcher configured, in response to a use request for resources of a physical network, the use request having a pair of nodes as terminal points designated among a plurality of nodes constituting the physical network, to search for one or more candidate paths between the terminal points, with which amounts of the resources related to the use request can be allocated, in a state where the resources that have already been allocated to one or more other use requests are set aside from the physical network; a calculator configured to calculate, for each of the one or more searched-for candidate paths, in a state where the resources are allocated to the candidate path, for each of the one or more other existing use requests to which the resources have already been allocated, a maximum number of paths that can be allocated between the terminal points related to the use request; and a selector configured to select the candidate path with which a sum total of the maximum numbers of paths becomes greatest.
 2. The resource allocation device as claimed in claim 1, wherein the calculator calculates, for each of the one or more existing use requests to which the resources have already been allocated, a value obtained by multiplying the maximum number of paths that can be allocated between the terminal points related to the use request, by a weight corresponding to the use request, and wherein the selector selects the candidate path with which the sum total of the maximum numbers of paths becomes greatest.
 3. A resource allocation method executed by a computer, the method comprising: a searching step, in response to a use request for resources of a physical network, the use request having a pair of nodes as terminal points designated among a plurality of nodes constituting the physical network, to search for one or more candidate paths between the terminal points, with which amounts of the resources related to the use request can be allocated, in a state where the resources that have already been allocated to one or more other use requests are set aside from the physical network; a calculating step to calculate, for each of the one or more searched-for candidate paths, in a state where the resources are allocated to the candidate path, for each of the one or more other existing use requests to which the resources have already been allocated, a maximum number of paths that can be allocated between the terminal points related to the use request; and a selecting step to select the candidate path with which a sum total of the maximum numbers of paths becomes greatest.
 4. The resource allocation method as claimed in claim 3, wherein the calculating step calculates, for each of the one or more existing use requests to which the resources have already been allocated, a value obtained by multiplying the maximum number of paths that can be allocated between the terminal points related to the use request, by a weight corresponding to the use request, and wherein the selecting step selects the candidate path with which the sum total of the maximum numbers of paths becomes greatest. 